ESLint: Fix testing-library/no-wait-for-multiple-assertions violations
#45067
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tyxla
added
[Type] Code Quality
tyxla
requested review from
Mamaduka,
mirka,
jsnajdr,
ciampo,
chad1008 and
ntsekouras
|
Size Change: 0 B Total Size: 1.27 MB ℹ️ View Unchanged
|
tyxla
deleted the
fix/eslint-testing-library/no-wait-for-multiple-assertions
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
This PR fixes all violations of the
testing-library/no-wait-for-multiple-assertionsrule, in preparation for enablingeslint-plugin-testing-libraryglobally for the project.See the plugin README for more info on the
testing-libraryESLint plugin.Why?
We've been improving our tests a lot recently with the migration to
@testing-library. One way we could improve them is to better standardize them and follow best practices whenever we can, and one of the best ways to get there is to follow the recommended ESLint rules of the libraries and utilities we use under the hood.How?
We're essentially fixing up a few instances where we either unnecessarily used
waitFor()around assertions, or had multiple assertions when only one is allowed.Testing Instructions
Verify all checks are green.
cc @brookewp as we've been discussing working to address some of those violations together.